Document path mapping mechanism

ABSTRACT

A method disclosed. The method includes receiving a Job Definition Format (JDF) job ticket indicating a document file to be printed is located in a JDF file path, mapping the JDF file path to a file path recognized at a print server, retrieving the document file and processing the document file for printing.

FIELD OF THE INVENTION

The invention relates to the field of printing systems, and inparticular, to print job management.

BACKGROUND

Printers are common peripheral devices attached to computers. A printerallows a computer user to make a hard copy of documents that are createdin a variety of applications and programs on a computer. To functionproperly, a channel of communication is established (e.g., via a networkconnection) between the printer and the computer to enable the printerto receive commands and information from the host computer.

Once a connection is established between a workstation and the printer,printing software is typically implemented at a print server to manage aprint job from job entry and management through the complete printingprocess. More frequently, Job Definition Format (JDF) is being used todescribe print jobs. JDF is an Extensible Markup Language (XML) basedfile format that describes a print job's characteristics (e.g.,quantity, paper type, data files, etc.).

JDF features job tickets that describe data files that are included in aprint job, as well as how the print job is to be printed. The jobtickets may also include an element (e.g., FileSpecURL) that specifiesan absolute path location of a document file. However, the specifiedpath may not be included on the server where the printing softwareresides. As a result, a print system user may need to map the file pathin the job ticket to a different file path on the server or mounteddrive.

Such mapping may not be possible since the user often does not haveaccess to the actual job ticket to be able to change the location.Further, the names of the mounted directories may change betweendifferent printing software servers and the user may want to customizeeach instance of the printing software.

Accordingly, a mechanism for mapping file paths from JDF to file pathswithin printing software is desired.

SUMMARY

In one embodiment, a method receiving a Job Definition Format (JDF) jobticket indicating a document file to be printed is located in a JDF filepath, mapping the JDF file path to a file path recognized at a printserver, retrieving the document file and processing the document filefor printing.

Another embodiment discloses a print server including a printingsoftware product. The printing software product includes a configurationfile to map a document file path indicated in a Job Definition Format(JDF) job ticket to a file path recognized by the print server.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained from thefollowing detailed description in conjunction with the followingdrawings, in which:

FIG. 1 illustrates one embodiment of a data processing system network;

FIG. 2 is a flow diagram illustrating one embodiment of saving aconfiguration file;

FIG. 3 is a flow diagram illustrating one embodiment of file pathmapping; and

FIG. 4 illustrates one embodiment of a computer system.

DETAILED DESCRIPTION

A file path mapping mechanism is described. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide a thorough understanding of thepresent invention. It will be apparent, however, to one skilled in theart that the present invention may be practiced without some of thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form to avoid obscuring the underlyingprinciples of the present invention.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the invention. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment.

FIG. 1 illustrates one embodiment of a data processing system network100. Network 100 includes a data processing system 102, which may beeither a desktop or a mobile data processing system, coupled viacommunications link 104 to network 106. In one embodiment, dataprocessing system 102 is a conventional data processing system includinga processor, local memory, nonvolatile storage, and input/output devicessuch as a keyboard, mouse, trackball, and the like, all in accordancewith the known art. In one embodiment, data processing system 102includes and employs the Windows operating system, or other operatingsystem, and/or network drivers permitting data processing system 102 tocommunicate with network 106 for the purposes of employing resourceswithin network 106.

Network 106 may be a local area network (LAN) or any other network overwhich print requests may be submitted to a remote printer or printserver. Communications link 104 may be in the form of a network adapter,docking station, or the like, and supports communications between dataprocessing system 102 and network 106 employing a network communicationsprotocol such as Ethernet, the AS/400 Network, or the like.

According to one embodiment, network 106 includes a print server 108that serves print requests over network 106 received via communicationslink 110 between print server 108 and network 106. Print server 108subsequently transmits the print requests via communications link 110 toone of printers 109 for printing, which are coupled to network 106 viacommunications links 111.

In one embodiment, the operating system on data processing system 102allows a user to select the desired print server 108 and submit requestsfor service requests to printer 109 via print server 108 over network106. In a further embodiment, print server 108 includes a print queuefor print jobs requested by remote data processing systems.

Although described as separate entities, other embodiments may includeprint server 108 being incorporated in one or more of the printers 109.However in other embodiments, the print server and printer may bephysically separate entities. Therefore, the data processing systemnetwork depicted in FIG. 1 is selected for the purposes of explainingand illustrating the present invention and is not intended to implyarchitectural limitations. Those skilled in the art will recognize thatvarious additional components may be utilized in conjunction with thepresent invention.

According to one embodiment, print server 108 implements a printingsoftware product that manages the printing of documents from dataprocessing system 102 between data processing system 102 and one or moreof printers 109. In other embodiments, the printing software productmanages printing of documents from multiple data processing systems 102to the one or more printers 109.

According to one embodiment, the printing software product may beimplemented using either InfoPrint Manager (IPM) or InfoPrintProcessDirector (IPPD), although other types of printing software may beused instead. In a further embodiment, data processing system 102includes a print application that interacts with the printing softwareproduct at printer server 108 to provide for efficient transmission ofprint jobs.

In one embodiment, the printing software product includes a graphicaluser interface (GUI) 120 that enables a system administrator (oroperator) to interact with the printing software product and printapplication. In such an embodiment, the print application generatesprint jobs in JDF as job tickets. As discussed above, JDF job ticketsmay implement file directory paths that are different from those in theprinting software product. Therefore in one embodiment, the printingsoftware product features a process that maps file paths from JDF tofile paths within the printing software product.

In such an embodiment, the printing software product provides aconfiguration file including mapping information. The mappinginformation is used by JDF during processing to allow the documentsspecified in JDF to point to a local path location, for example, and yetbe mapped to a location that is visible to the printing software productwithout having to change the JDF.

In one embodiment, a sample configuration file is provided with theprinting software product. In such an embodiment, the sampleconfiguration file converts all Windows style file paths (e.g. “C:\”) toLinux and AIX style file paths (e.g. “/”). In a further embodiment, theconfiguration file may be subsequently modified by an operator. Forinstance, the operator may modify the contents of the configuration fileusing GUI 120. Alternatively, the operator may use GUI to specify a newconfiguration file to be used. In one embodiment of network 100printing, the printing software product attempts each mapping in theconfiguration file by making the specified mapping substitutions, untila file is found successfully.

According to one embodiment, the configuration file includes one mappingper line. In this embodiment, the client value is on the left and thehost value is on the right, separated by a semi-colon. In a furtherembodiment, leading and trailing blanks are removed from each side. Eachdirectory name includes at least one “\” or “/”. In yet a furtherembodiment, directories are treated as complete directory names (e.g., a“\” or “/” is added to the end if not already present). In still afurther embodiment, an asterisk (*) is allowed on the client side as aDrive Letter indicator to match any specified Drive.

Based on the above specified format, an exemplary sample configurationfile provided with the printing software product would include the asample line (*:\;/), which will convert any Windows style directory to alinux/aix style directory. Table 1 shows an exemplary configuration fileafter modification, where the file includes direct mapping lines addedby an operator, as well as the sample line.

TABLE 1 C:\testfiles;/BankFiles/testfiles Added by operatorC:\production\siteA;/BankFiles/prod Added by operatorC:\production\siteA\test\;/BankFiles/test Added by operator*:\production\siteA\test\;/BankFiles/test Added by operator *:\;/ Sample

FIG. 2 is a flow diagram illustrating one embodiment of loading aconfiguration file in the printing software product at print server 108.At processing block 210, the printing software product parses theconfiguration file. At processing block 220, the configuration file isloaded into memory. At decision block 230, it is determined whetherupdates are made to the configuration file some time after the file isloaded into memory.

As discussed above, updates may include changes made via GUI 120 to thecurrent file, or that a new/different file is specified. In oneembodiment, a routine is performed at a predetermined interval (e.g.,minute) to check for updates. If updates to the configuration are found,control is returned to processing blocks 210 and 220 where theconfiguration file is again parsed and the loaded version in the memoryis refreshed. However if no updates are found the printing softwareproduct is ready to perform file path mapping, processing block 240.

FIG. 3 is a flow diagram illustrating one embodiment of file pathmapping. At processing block 310, the printing software product receivesa JDF job ticket specifying an absolute path location of a documentfile. At processing block 320, the configuration file loaded into thememory is searched for a mapping. At decision block 330, it isdetermined whether the document file is in a path specified by a directmapping line entered into the configuration file by an operator.

If the document file is found in the path specified by one of severaldirect mapping lines, the document file is retrieved and processed bythe printing software product for printing, processing block 360.Otherwise, it is determined whether the document file is in a pathspecified by the sample line, decision block 340. If the document fileis found in the path specified by the sample line, control is returnedto processing block 360 where the document file is retrieved andprocessed for printing.

If the document file is not found in the path specified by the sampleline, it is determined whether the document file is in a hot folderlocation. A hot folder is a printing application that enables a documentto be immediately printed upon being inserted into a folder. If thedocument file is found in the hot folder, control is again returned toprocessing block 360 where the document file is retrieved and processedfor printing. However if the document file is not in the hot folder thefile is not found, processing block 370. Subsequently, an error messagemay be provided to the operator.

Using the sample configuration file entries shown in Table 1 toillustrate operation upon receiving a JDF including the file name“C:\testfiles \test1.pdf”, the printing software product would find amatch for “C:\testfiles” on the left side of line 1, and substitute“/BankFiles/testfiles” from the right side of the line and first lookfor file /BankFiles/testfiles/test1.pdf. Subsequently, the printingsoftware product would find a match for “*:\” and substitute “/” andcheck for file “/testfiles/test1.pdf”. Finally, the printing softwareproduct would check the hot folder location for a file named“test1.pdf”.

Using another example, the printing software product would first lookfor the file “/BankFiles/prod/test/justAtest.pdf” upon receiving a JDFincluding the file name “C:\production \siteA \test \justAtest.pdf”(e.g., the software product found a match for “C:\production \siteA” onthe left side of line 2, and substituted “/BankFiles/prod” from theright side of the line). Next the printing software product would find amatch for “C:\production \siteA \test” on the left side of line 3, andsubstitute “/BankFiles/test” from the right side and look for file/BankFiles/test/justAtest.pdf”. (The same search happens for line 4because the * would cause a match on drive C.) Next the printingsoftware product would find a match for “*:\” on the left side of line5, and substitute “1” from the right side and look for file“/production/siteA/test/justAtest.pdf” before checking the hot folderlocation for a file named “justAtest.pdf”.

As yet another example, the printing software product would first lookfor the file “/BankFiles/test/justAtest.pdf” upon receiving a JDFincluding the file name “K:\production \siteA \test \justAtest.pdf(e.g., the software product found a match for “*:\production \siteA\test” on the left side of line 4, and substituted “/BankFiles/test”from the right side of the line). Then, the printing software productwould find a match for “*:\” on the left side of line 5, and substitute“/” from the right side and look for file“/production/siteA/test/justAtest.pdf”. Finally, it would check the hotfolder location for a file named “justAtest.pdf”.

FIG. 4 illustrates a computer system 400 on which data processing system102 and/or server 108 may be implemented. Computer system 400 includes asystem bus 420 for communicating information, and a processor 410coupled to bus 420 for processing information.

Computer system 400 further comprises a random access memory (RAM) orother dynamic storage device 425 (referred to herein as main memory),coupled to bus 420 for storing information and instructions to beexecuted by processor 410. Main memory 425 also may be used for storingtemporary variables or other intermediate information during executionof instructions by processor 410. Computer system 400 also may include aread only memory (ROM) and or other static storage device 426 coupled tobus 420 for storing static information and instructions used byprocessor 410.

A data storage device 425 such as a magnetic disk or optical disc andits corresponding drive may also be coupled to computer system 400 forstoring information and instructions. Computer system 400 can also becoupled to a second I/O bus 450 via an I/O interface 430. A plurality ofI/O devices may be coupled to I/O bus 450, including a display device424, an input device (e.g., an alphanumeric input device 423 and or acursor control device 422). The communication device 421 is foraccessing other computers (servers or clients). The communication device421 may comprise a modem, a network interface card, or other well-knowninterface device, such as those used for coupling to Ethernet, tokenring, or other types of networks.

Embodiments of the invention may include various steps as set forthabove. The steps may be embodied in machine-executable instructions. Theinstructions can be used to cause a general-purpose or special-purposeprocessor to perform certain steps. Alternatively, these steps may beperformed by specific hardware components that contain hardwired logicfor performing the steps, or by any combination of programmed computercomponents and custom hardware components.

Elements of the present invention may also be provided as amachine-readable medium for storing the machine-executable instructions.The machine-readable medium may include, but is not limited to, floppydiskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs,RAMs, EPROMs, EEPROMs, magnetic or optical cards, propagation media orother type of media/machine-readable medium suitable for storingelectronic instructions. For example, the present invention may bedownloaded as a computer program which may be transferred from a remotecomputer (e.g., a server) to a requesting computer (e.g., a client) byway of data signals embodied in a carrier wave or other propagationmedium via a communication link (e.g., a modem or network connection).

Whereas many alterations and modifications of the present invention willno doubt become apparent to a person of ordinary skill in the art afterhaving read the foregoing description, it is to be understood that anyparticular embodiment shown and described by way of illustration is inno way intended to be considered limiting. Therefore, references todetails of various embodiments are not intended to limit the scope ofthe claims, which in themselves recite only those features regarded asessential to the invention.

What is claimed is:
 1. A method comprising: receiving a Job DefinitionFormat (JDF) job ticket indicating a document file to be printed islocated in a JDF file path; mapping the JDF file path to a file pathrecognized at a print server by accessing one or more mapping lines in aconfiguration file; retrieving the document file; and processing thedocument file for printing.
 2. The method of claim 1 further comprisingmapping the JDF file path to a file path specified by a direct mappingline in the configuration file.
 3. The method of claim 2 furthercomprising mapping the JDF file path to a file path specified by asample line in the configuration file if the document file is not foundin the file path specified by a direct mapping line.
 4. The method ofclaim 3 further comprising mapping the JDF file path to a hot folder ifthe document file is not found in the file path specified by the sampleline.
 5. The method of claim 4 further comprising generating anotification that the document file cannot be found if the document fileis not found in the hot folder.
 6. The method of claim 1 wherein the JDFfile path is a file specified in a first operating system and the filepath recognized at the print server is a file specified in a secondoperating system.
 7. The method of claim 1 further comprising: parsingthe configuration file prior to receiving the JDF job ticket; andloading the configuration file into memory.
 8. The method of claim 7further comprising checking for updates to the configuration file atpredetermined intervals.
 9. The method of claim 8 wherein updates aremade to the configuration file using a graphical user interface (GUI).10. A print server comprising a processor and a printing softwareproduct to receive a Job Definition Format (JDF) job ticket indicatingthat a document file to be printed is located in a JDF file path, theprinting software product having a configuration file to map thedocument file path to a file path recognized by the print server byparsing the configuration file and loading the configuration file into amemory after the configuration file is modified.
 11. The print server ofclaim 10 wherein the printing software product retrieves a document filefrom the file path recognized by the print server and processes thedocument file for printing.
 12. The print server of claim 11 wherein theprinting software product further comprises a graphical user interface(GUI) to enable a user to modify the configuration file.
 13. The printserver of claim 10 further wherein the printing software product maps aJDF file path to a file path specified by a direct mapping line in theconfiguration file.
 14. The print server of claim 13 further wherein theprinting software product maps the JDF file path to a file pathspecified by a sample line in the configuration file if the documentfile is not found in the file path specified by a direct mapping line,and maps the JDF file path to a hot folder if the document file is notfound in the file path specified by the sample line.
 15. An article ofmanufacture comprising a non-transitory machine-readable mediumincluding data that, when accessed by a machine, cause the machine toperform operations comprising: receiving a Job Definition Format (JDF)job ticket indicating a document file to be printed is located in a JDFfile path; mapping the JDF file path to a file path recognized at aprint server by accessing one or more mapping lines in a configurationfile; retrieving the document file; and processing the document file forprinting.
 16. The article of manufacture of claim 15 when accessed bythe machine, further cause the machine to perform operations comprisingmapping the JDF file path to a file path specified by a direct mappingline in the configuration file.
 17. The article of manufacture of claim16 when accessed by the machine, further cause the machine to performoperations comprising mapping the JDF file path to a file path specifiedby a sample line in the configuration file if the document file is notfound in the file path specified by a direct mapping line.
 18. Thearticle of manufacture of claim 17 when accessed by the machine, furthercause the machine to perform operations comprising mapping the JDF filepath to a hot folder if the document file is not found in the file pathspecified by the sample line.